Requirements for Running the AppleShare Client 3.8 Software
Installing the AppleShare Client 3.8 Software
Key Changes from AppleShare Client 3.7.2 & 3.7.4
Using the New Features of the AppleShare Client 3.8 Software
Known Incompatibilities and Limitations
Introduction
AppleShare Client 3.8 is the latest version of AppleShare Client software. (Previous versions of the AppleShare Client software were known as the AppleShare Workstation Software.)
Requirements for Running the AppleShare Client 3.8 Software
• System Software: 7.6 or later
• Networking Software: Open Transport 1.1.2 or later
In order for AutoRemounter functionality to work properly, AppleShare Client 3.8 requires a new version of the AutoRemounter Control Panel. AutoRemounter 1.3 ships with System 8.1.
Computers that are running system software earlier than system software 7.5.1 should use AppleShare Workstation 3.5. Computers that are running system software 7.5.1 or later (up to but not including 7.5.3) should use AppleShare Workstation 3.6.5. Computers running system software 7.6 or
later should use AppleShare Client 3.8.
Installing the AppleShare Client 3.8 Software
1. Make sure that system software 7.6 or later and Open Transport 1.1.2 or later are installed on your computer.
2. Open the Installer by double-clicking the Installer icon.
3. Follow the instructions displayed by the Installer.
4. If you wish to use TCP/IP make sure that the TCP/IP control panel is set up correctly.
The AppleShare Client Installer places the appropriate localized AppleShare Chooser extension in the Extensions folder inside the System Folder.
If you are running a non US English System, Do Not use the installer. The localized versions in the International folder are place holders. If you accidentally install a localized version, trying to log on to a server will cause a User Break into MacsBug at NewStatus + B6. Drag install the US version of the AppleShare Client from the top level of the AppleShare folder into the Extensions folder in the active System folder and reboot.
Key Changes from AppleShare Client 3.7.2 & 3.7.4
• Works correctly with the AutoRemounter 1.3 control panel.
• Dialogs center correctly when the user has more than one monitor.
• Aliases made of servers mounted via AppleTalk will not try to switch to TCP/IP. If
you want a TCP/IP alias, you must first mount the server via TCP/IP.
• Much of the Login process is asynchronous, you can cancel out of the connection attempt.
If the Appearance manager is present you can switch layers while the connection is being
established.
• The 3.8 Client supports a new, transport independant UAM (User Authentication Module)
Interface. This allows UAM plug-in modules to connect to Servers using AFP over TCP/IP.
Using the New Features of the AppleShare Client 3.8 Software
The AppleShare Client 3.8 software automatically uses TCP to make connections when users choose an AppleShare IP file server that is set up for TCP connections. If you want to use AppleTalk to make the connection, press the Option key when you double-click the name of an AppleShare IP file server in the “Select a file server” list in the Chooser window or when you click the OK button in the Chooser window.
When you want to use TCP to connect to an AppleShare IP file server that does not appear in the “Select a file server” list in the Chooser window, click the Server IP Address button. When you click the Server IP Address button, a dialog box appears in which you can type the DNS name (such as shasta.acme.com) or the IP address of the AppleShare IP file server (such as 172.16.156.52).
If the AppleShare IP file server is running on a computer behind a firewall, you can reach it by appending a colon (:) and the TCP port number (by default, 548) to the IP address or DNS name.
Known Incompatibilities and Limitations
• If you have problems using AppleShare Client 3.8 to connect to an AppleShare IP file server, use MacTCP Ping (available from Apple Computer) to make sure that you can ping the computer that is running the AppleShare IP file server software. If you can’t ping successfully, there is a connectivity problem. Check cabling and the configuration of the TCP/IP control panel.
• AppleShare Client 3.8 is not compatible with versions of RunShare prior to version 3.0. Computers on which they are both installed will crash. Be sure to upgrade to RunShare version 3.0 or later before you install the AppleShare Client 3.8 software.
• If a user makes an alias to an AppleShare IP volume and uses TCP to connect to that volume, AppleTalk must be active on the user’s computer. AppleTalk must be active due to a bug in the Alias manager.
• The AppleShare IP 5.0 Web & File Server uses a new set of access privileges based on combinations of the original access privileges (See Files, See Folders, and Make Changes). The new privileges are Read Only, Read & Write, Write Only, and None. When you connect to an AppleShare IP file server volume and choose Sharing from the Finder’s File menu, the dialog box that appears displays the original AppleShare access privileges. If you use the dialog box to change a folder’s privileges to a combination of privileges that is invalid on the AppleShare IP file server, the file server automatically applies the most secure access privilege that approximates the change. If you close the dialog box and choose Sharing again, the checkboxes that are checked may be different than the checkboxes that you checked earlier. Mac OS 8 Finder Sharing dialog box uses the AppleShare IP access privilege model.
• When you install Open Transport 1.1.2 on a PowerBook 3400, immediately install the Mac OS 7.6.1 Update for PowerBook 3400. The update fixes a problem that could cause crashes when you switch between Infrared and LocalTalk.
• Some old HyperCard XCMDs that mount AppleShare volumes are incompatible with the AppleShare Client 3.8 software.
• Microsoft Office Manager causes the AppleShare Client 3.7 software to crash when you try to connect to an AppleShare file server. To correct this problem, install Office Manager Updater, available from Microsoft.
• NetWare User Authentication Modules (UAMs) earlier that 5.11 are incompatible with AppleShare Client 3.7 and later. Contact Novell for an update.
• Utilities that mount disk images from AppleShare File Servers may have problems with the AppleShare Client 3.8 software. If you have problems, contact the vendor for a new version.
• Versions of Santorini Server Manager earlier than 4.0 are not fully functional when used with the AppleShare Client 3.8 software. Santorini Server Manager 4.0 is available on the AppleShare IP 5.0 Companion CD-ROM disc. Otherwise, contact Santorini for an update.
• Server management applications that mount AppleShare volumes may have problems with the AppleShare Client 3.8 software. Contact the vendor for an update.
• If there are volumes set to mount at startup and the server administrator disables the "Enable users to save password for automatic log on" checkbox in Web & File Admin, you will be unable to change the startup mounting settings for those volumes.
• In order to allow startup mounting via TCP be sure to delete the AppleShare prep file in the preferences folder, and reselect the volumes you wish to have mount at startup. This insures that the TCP address of the server will be saved in the AppleShare prep file.
• If you are having problems making the Client use TCP/IP for startup mounting try setting TCP/IP to always load. If that doesn't work try turning on VM (this will allow the OT libraries to load in less memory).
• If you have a pre ASIP 5.0 server set to mount at startup and the server is upgraded to ASIP 5.0 (or later), You should throw away the AppleShare Prep file and reselect the server volumes you wish to mount at startup. This will prevent problems with server volumes mounting twice.
• If you are receiving "Server not responding" errors when connecting via TCP over PPP, use the AppleShare Client Setup utility (available on the AppleShare IP website URL:<http://www.apple.com/appleshareip/>) to increase the TCP Lookup timeout from 20 seconds to the time it takes your PPP link to come up plus 20 seconds.
• If the Chooser freezes for 2 minutes when trying to connect to a TCP server, use the AppleShare Client Setup utility (available on the AppleShare IP website URL:<http://www.apple.com/appleshareip/>) to reduce the TCP Connect Timeout from 120 seconds to 20 seconds. Reducing the TCP Connect Timeout may make connecting to AFP servers over the Internet impossible.
• If you have TCP/IP set to use PPP to connect, and open an alias to an ASIP server (or any other that supports AFP over TCP/IP), the Client will try to connect using TCP/IP first before using AppleTalk. If you do not want this, you may use the the AppleShare Client Setup utility (available on the AppleShare IP website URL:<http://www.apple.com/appleshareip/>) to disable TCP/IP support in the Client.
• If you have an alias to a server that supports AFP over TCP/IP, and the server is behind a firewall that dosn't allow pings through, you will not be able to connect via the alias unless you use the AppleShare Client Setup utility (available on the AppleShare IP website URL:<http://www.apple.com/appleshareip/>) to disable address verification via pings.
• If you have a Global Village K56 flex card modem and are using OT PPP 1.0.1 to provide TCP/IP connectivity, you need to disable the menubar status lights, or launch PPP manually and connect to your ISP, before using the Chooser to connect to an AppleShare file server over TCP/IP.
• If the Chooser hangs when mounting volumes (after the OK button has been clicked in the
volume list dialog). Try disabling the Apple Menu Options Control Panel.
• If you experience crashes wile mounting a volume as the Administrator after you have mounted a sharepoint contained on the volume as a regular user, be sure to mount a different volume in between. So the sequence should be mount sharepoint as user, unmount sharepoint, mount other server volume, mount volume as administrator, unmount other volume. This bug will be fixed in a future version of the Finder
